![]() |
![]() |
![]() |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
![]() |
![]() |
To access the contents, click the chapter and section titles.
Oracle Performance Tuning and Optimization
SummaryThis chapter discussed many concepts and ideas you can use to further enhance performance. Chapter 9, Oracle Instance Tuning, was interested in instance tuning in generalthings that always applied. This chapter began to look at more specific topics that may or may not apply, depending on your configuration. In fact, some of the things described in this chapter can hurt performance if they are not handled correctly. Clusters and indexes are very useful when the application can take advantage of them. In update-intensive applications where indexes are used, indexes can degrade performance because they must be updated along with the data. Similarly, clusters can be beneficial if the data access patterns use the cluster, else they can be a burden. The Oracle Parallel Query option and the Parallel Server option can offer significant performance benefits. The Parallel Query option provides a mechanism to improve system utilization by splitting queries into multiple processes. The Parallel Server option provides a robust scaleable clustering option that can increase both performance and provide instantaneous failover capabilities. Your applications and needs will determine whether these options can benefit you. When tuning a system, it is important to remember the risks you are taking. The last chapter discussed different tuning topics such as shared pool size and database block buffer size. Increasing the size of the shared pool and block buffers can increase cache hits; it also has very little risk of hurting performance. However, some of the topics addressed in this chapter may hurt performance if they are not configured correctly. You must assess the risks involved whenever you reconfigure, especially if this reconfiguration is going into production without intensive testing. If you think about what you are changing and what those changes will affectand if you understand the data access patterns of your applicationsyou minimize the risks. Think about how the changes you are making will affect the system. Try to understand how your applications will react. By doing so, you minimize risks and optimize results.
|
![]() |
Products | Contact Us | About Us | Privacy | Ad Info | Home
Use of this site is subject to certain Terms & Conditions, Copyright © 1996-2000 EarthWeb Inc. All rights reserved. Reproduction whole or in part in any form or medium without express written permission of EarthWeb is prohibited. |